Wireless communication framework for multiple user equipment

ABSTRACT

The described technology is generally directed towards operating a user equipment node as a scheduler user equipment (e.g., which can be a local manager of other nodes in a group). The scheduler user equipment receives a scheduling request for the scheduling of the resources for transmission of data by a transmitter user equipment, and based on the traffic type requested, schedules the transmitter user equipment and receiver user equipment(s) with scheduling data/allocated radio resources. The transmitter user equipment can directly transmit to the receiver user equipment(s) on the allocated radio resources, e.g., without further involvement of the scheduler user equipment/local manager. For cellular data, the scheduler user equipment can schedule the transmitter user equipment to transmit to the scheduler user equipment as a receiver node.

TECHNICAL FIELD

The subject application is related to wireless communication systems,and, for example, to a wireless communication framework for multipleuser equipment in vehicle-to-everything (V2X) communications.

BACKGROUND

In LTE wireless communication systems, vehicle-to-everything (V2X)generally utilizes the Sidelink interface, alternatively referred to asPC5, to enable V2X communications, including V2V (vehicle-to-vehicle)communications, V21 (vehicle-to-infrastructure) communications, V2P(vehicle-to-pedestrian) communications and V2N (vehicle-to-network)communications. The PC5 interface is built based on a mesh architectureof peer-to-peer device communication. LTE V2X also supports Uu interface(the radio interface between the mobile device and the radio accessnetwork) enhancement to assist the PC5 communications.

Existing (e.g., PC5-based) interfaces assume a mesh architecture inwhich every node is a peer to each other. This approach does not rely onany network infrastructure. However, spectrum efficiency cannot be veryhigh because of the peer-to-peer structure. Another drawback of thismesh architecture is that it is not compatible with infrastructure-basedcellular networks that utilize a hierarchical architecture. As a result,a separate spectrum needs to be obtained to deploy a V2X service basedon a peer-to-peer mesh network architecture, which is very costly.

BRIEF DESCRIPTION OF THE DRAWINGS

The technology described herein is illustrated by way of example and notlimited in the accompanying figures in which like reference numeralsindicate similar elements and in which:

FIG. 1 illustrates an example wireless communication system in which onenode (a scheduler user equipment) broadcasts its scheduling ability andschedules another node (a transmitter user equipment) for transmissionto receiver node(s), in accordance with various aspects andimplementations of the subject disclosure.

FIG. 2 illustrates an example wireless communication system in which ascheduler user equipment schedules a transmitter user equipment and areceiver user equipment for a direct unicast transmission, in accordancewith various aspects and implementations of the subject disclosure.

FIG. 3 illustrates an example wireless communication system in which ascheduler user equipment schedules a transmitter user equipment andreceiver user equipments for a broadcast (or multicast) transmission, inaccordance with various aspects and implementations of the subjectdisclosure.

FIG. 4 illustrates an example wireless communication system in which ascheduler user equipment schedules a transmitter user equipment totransmit cellular data to the scheduler user equipment (as a receivernode), in accordance with various aspects and implementations of thesubject disclosure.

FIGS. 5-7 comprise a flow diagram of example operations of a scheduleruser equipment, in accordance with various aspects and implementationsof the subject disclosure.

FIG. 8 illustrates a flow diagram of example transmitter/receiver userequipment operations for working with a scheduler user equipment, inaccordance with various aspects and implementations of the subjectdisclosure.

FIG. 9 illustrates an example flow diagram of scheduler user equipmentoperations, in accordance with various aspects and implementations ofthe subject disclosure.

FIG. 10 illustrates an example flow diagram of transmitter userequipment operations, in accordance with various aspects andimplementations of the subject disclosure.

FIG. 11 illustrates an example flow diagram of scheduler user equipmentoperations, e.g., embodied as instructions executable by a processor, inaccordance with various aspects and implementations of the subjectdisclosure.

FIG. 12 illustrates an example block diagram of an example mobilehandset operable to engage in a system architecture that facilitateswireless communications according to one or more embodiments describedherein.

FIG. 13 illustrates an example block diagram of an example computeroperable to engage in a system architecture that facilitates wirelesscommunications according to one or more embodiments described herein.

DETAILED DESCRIPTION

Briefly, one or more aspects of the technology described herein aregenerally directed towards multiple party (e.g., three party)communication. As will be understood, a third node, (other than thetransmitter user equipment and receiver user equipment), referred toherein as a scheduler user equipment, acts as a local resourcecoordinator for a group of user equipment nodes with respect tocoordinating their radio resource usage. More particularly, while thescheduling/resource allocation can be performed by a local resourcecoordinator/local manager node (the scheduler user equipment), the datatransmission can be done by different user equipment nodes in adistributed manner, which can be a direct data transmission between atransmitter and one or more receivers. As used herein, “direct” datatransmission means that no intervening node (including the scheduleruser equipment, network device and so on) necessarily needs to beinvolved; however, as described herein the radio resources arescheduled, and thereby avoid or significantly reduce the chances ofinterference that often occurs with indiscriminate meshdevice/peer-to-peer communications.

In one or more implementations, the third/centralized local manager nodeis thus referred to herein as a scheduler user equipment, while theother nodes (in a three party example) are referred to as a transmitteruser equipment and a receiver user equipment. The scheduler userequipment broadcasts synchronization signals (Synchronization SignalBloc, or SSB, and Tracking Reference Signal, or TRS) to surrounding userequipments. The broadcasting information includes the resource poolinformation.

Other nodes synchronize with the scheduler user equipment and receivethe broadcast information.

When a transmitter user equipment has some V2X (vehicle-to-everything)traffic data packet(s), the transmitter user equipment sends ascheduling request to the scheduler user equipment. In one or moreimplementations, the scheduling request includes the traffic type, whichcan comprise V2X broadcast or multi-cast traffic, cellular traffic orV2X unicast traffic (which additionally identifies the designatedreceiver user equipment for the targeted unicast traffic).

Upon receiving the scheduling request, the scheduler user equipmentstarts to schedule radio resources. In one or more implementations, thescheduling decision is transmitted as DCI (Downlink Control Information)from the scheduler user equipment to the transmitter user equipment andthe receiver user equipment(s). The DCI may include the resourceallocation, MCS, precoder, and so forth.

Upon receiving DCI, the transmitter user equipment is to transmit dataon the allocated radio resource while receiver user equipment(s) isintended to receive data on the allocated radio resources. For unicastV2X traffic, the designated receiver user equipment is picked accordingto the receiver identified in the scheduling request. For broadcast V2Xtraffic, the receive DCI is broadcast to all surrounding userequipments, while for multi-cast traffic, the receive DCI is transmittedto a group of user equipments.

By way of example, consider that a user equipment wants to broadcastsome local traffic-related information to one or more other userequipments. The user equipment does not need this information to go tothe core network, just to locally neighboring user equipments. The userequipment thus becomes a transmitter user equipment, and requests datatransmission resources for a broadcast communication, from the scheduleruser equipment with which the transmitter user equipment hassynchronized. The scheduler user equipment coordinates this request withany other scheduled transmission resources it has allocated, andallocates the resources by sending scheduling data to the transmitteruser equipment and also schedulers the receiver user equipment(s). Thetransmitter user equipment then broadcasts the traffic-related data tothe receiver user equipment(s) based on the scheduling data.

For cellular data, the scheduler user equipment is also the receivernode. In one alternative, if the scheduler user equipment has IAB(Integrated Access and Backhaul) or mobile relay functionality, then thecommunication between the transmitter user equipment and the scheduleruser equipment becomes an access link (e.g., as used by conventionalcellular user equipments) and the data is relayed over a backhaul linkto another IAB node or donor node (e.g., a node with wired cellular corenetwork connectivity). In another alternative the link between thescheduler user equipment and the transmitter user equipment utilizesSidelink control formats and data transmission formats.

It should be understood that any of the examples and terms used hereinare non-limiting. For instance, the examples are based on New Radio (NR,sometimes referred to as 5G) communications between a user equipmentexemplified as a vehicle device, a smartphone or the like and a networkdevice; however virtually any communications devices may benefit fromthe technology described herein, and/or their use in different spectrumsmay likewise benefit. Notwithstanding, these are non-limiting examples,and any of the embodiments, aspects, concepts, structures,functionalities or examples described herein are non-limiting, and thetechnology may be used in various ways that provide benefits andadvantages in radio communications in general.

In some embodiments the non-limiting term “radio network node” or simply“network node,” “radio network device or simply “network device” is usedherein. These terms may be used interchangeably, and refer to any typeof network node that serves user equipment and/or connected to othernetwork node or network element or any radio node from where userequipment receives signal. Examples of radio network nodes are Node B,base station (BS), multi-standard radio (MSR) node such as MSR BS,gNodeB, eNode B, network controller, radio network controller (RNC),base station controller (BSC), relay, donor node controlling relay, basetransceiver station (BTS), access point (AP), transmission points,transmission nodes, RRU, RRH, nodes in distributed antenna system (DAS)etc.

In some embodiments the non-limiting term user equipment (UE) is used.It refers to any type of wireless device that communicates with a radionetwork node in a cellular or mobile communication system. Examples ofuser equipment are target device, device to device (D2D) user equipment,machine type user equipment or user equipment capable of machine tomachine (M2M) communication, PDA, Tablet, mobile terminals, smart phone,laptop embedded equipped (LEE), laptop mounted equipment (LME), USBdongles etc.

Some embodiments are described in particular for 5G new radio systems.The embodiments are however applicable to any radio access technology(RAT) or multi-RAT system where the user equipment operates usingmultiple carriers e.g. LTE FDD/TDD, WCMDA/HSPA, GSM/GERAN, Wi Fi, WLAN,WiMax, CDMA2000 etc.

The embodiments are applicable to single carrier as well as tomulticarrier (MC) or carrier aggregation (CA) operation of the userequipment. The term carrier aggregation (CA) is also called (e.g.interchangeably called) “multi-carrier system”, “multi-cell operation”,“multi-carrier operation”, “multi-carrier” transmission and/orreception.

Note that the solutions outlined equally applies for Multi RAB (radiobearers) on some carriers (that is data plus speech is simultaneouslyscheduled).

As is known, instead of having a peer-to-peer mesh network, recentwireless radio technology provides the ability promote a UE (which canbe a special type of UE such as a Vehicle or Road-side Unit) to act aslocal manager for a group of neighboring UEs. A local manager can act arelay node. The local manager can provide access to UEs, and canschedule UEs over a Sidelink interface with radio resources from aresource pool granted by the network, while maintaining a hierarchicalnetwork architecture which can be used in conjunction withinfrastructure-based IAB deployments. Note that it is also known that alocal manager can be elected by other neighboring UEs without networkinvolvement. In one aspect, such a local manager can operate as ascheduling user equipment as described herein.

FIG. 1 illustrates an example wireless communication system 100 inaccordance with various aspects and embodiments of the subjecttechnology. In one or more embodiments, the system 100 can comprise oneor more user equipments; three such user equipments 102(1)-102(3) areexemplified in FIG. 1.

The user equipment 102(1) is the scheduler user equipment, which can beoperating as a local manager, or acting on behalf of a local manager. Inthe example shown, the scheduler user equipment 102(1) couples to thenetwork 104 (e.g., any network device or devices). The scheduler userequipment 102(1) communicates with the network 104, and in turn to oneor more communication service provider networks 112. In variousembodiments, the system 100 is or comprises a wireless communicationnetwork serviced by one or more wireless communication networkproviders. In example embodiments, a user equipment (collectively orindividually 102) can be communicatively coupled to the wirelesscommunication network via a network device 104 (e.g., network node). Thenetwork device 104 can communicate with a user equipment (UE) 102, thusproviding connectivity between the user equipment and the wider cellularnetwork.

In example implementations, each user equipment 102 such as the userequipment 102(1) is able to send and/or receive communication data via awireless link to the network device 104. The system 100 can thus includeone or more communication service provider networks 112 that facilitateproviding wireless communication services to various user equipment,including user equipments 102(1)-102(3), via the network device 104and/or various additional network devices (not shown) included in theone or more communication service provider networks 112. The one or morecommunication service provider networks 112 can include various types ofdisparate networks, including but not limited to: cellular networks,femto networks, picocell networks, microcell networks, internet protocol(IP) networks Wi-Fi service networks, broadband service network,enterprise networks, cloud based networks, and the like. For example, inat least one implementation, system 100 can be or include a large scalewireless communication network that spans various geographic areas.According to this implementation, the one or more communication serviceprovider networks 112 can be or include the wireless communicationnetwork and/or various additional devices and components of the wirelesscommunication network (e.g., additional network devices and cell,additional user equipments, network server devices, etc.).

The network device 104 can be connected to the one or more communicationservice provider networks 112 via one or more backhaul links or thelike. For example, the one or more backhaul links can comprise wiredlink components, such as a T1/E1 phone line, a digital subscriber line(DSL) (e.g., either synchronous or asynchronous), an asymmetric DSL(ADSL), an optical fiber backbone, a coaxial cable, and the like. Theone or more backhaul links 108 can also include wireless linkcomponents, such as but not limited to, line-of-sight (LOS) or non-LOSlinks which can include terrestrial air-interfaces or deep space links(e.g., satellite communication links for navigation).

The wireless communication system 100 can employ various cellularsystems, technologies, and modulation schemes to facilitate wirelessradio communications between devices (e.g., a user equipment 102 and thenetwork device 104). While example embodiments might be described for 5Gnew radio (NR) systems, the embodiments can be applicable to any radioaccess technology (RAT) or multi-RAT system where the user equipmentoperates using multiple carriers e.g. LTE FDD/TDD, GSM/GERAN, CDMA2000etc. For example, the system 100 can operate in accordance with globalsystem for mobile communications (GSM), universal mobiletelecommunications service (UMTS), long term evolution (LTE), LTEfrequency division duplexing (LTE FDD, LTE time division duplexing(TDD), high speed packet access (HSPA), code division multiple access(CDMA), wideband CDMA (WCMDA), CDMA2000, time division multiple access(TDMA), frequency division multiple access (FDMA), multi-carrier codedivision multiple access (MC-CDMA), single-carrier code divisionmultiple access (SC-CDMA), single-carrier FDMA (SC-FDMA), orthogonalfrequency division multiplexing (OFDM), discrete Fourier transformspread OFDM (DFT-spread OFDM) single carrier FDMA (SC-FDMA), Filter bankbased multi-carrier (FBMC), zero tail DFT-spread-OFDM (ZT DFT-s-OFDM),generalized frequency division multiplexing (GFDM), fixed mobileconvergence (FMC), universal fixed mobile convergence (UFMC), uniqueword OFDM (UW-OFDM), unique word DFT-spread OFDM (UW DFT-Spread-OFDM),cyclic prefix OFDM CP-OFDM, resource-block-filtered OFDM, Wi Fi, WLAN,WiMax, and the like. However, various features and functionalities ofsystem 100 are particularly described wherein the devices (e.g., theuser equipments 102 and the network device 104) of system 100 areconfigured to communicate wireless signals using one or more multicarrier modulation schemes, wherein data symbols can be transmittedsimultaneously over multiple frequency subcarriers (e.g., OFDM, CP-OFDM,DFT-spread OFMD, UFMC, FMBC, etc.). The embodiments are applicable tosingle carrier as well as to multicarrier (MC) or carrier aggregation(CA) operation of the user equipment. The term carrier aggregation (CA)is also called (e.g. interchangeably called) “multi-carrier system”,“multi-cell operation”, “multi-carrier operation”, “multi-carrier”transmission and/or reception. Note that some embodiments are alsoapplicable for Multi RAB (radio bearers) on some carriers (that is dataplus speech is simultaneously scheduled).

In various embodiments, the system 100 can be configured to provide andemploy 5G wireless networking features and functionalities. With 5Gnetworks that may use waveforms that split the bandwidth into severalsub bands, different types of services can be accommodated in differentsub bands with the most suitable waveform and numerology, leading toimproved spectrum utilization for 5G networks. Notwithstanding, in themmWave spectrum, the millimeter waves have shorter wavelengths relativeto other communications waves, whereby mmWave signals can experiencesevere path loss, penetration loss, and fading. However, the shorterwavelength at mmWave frequencies also allows more antennas to be packedin the same physical dimension, which allows for large-scale spatialmultiplexing and highly directional beamforming.

Turning to aspects related to the use of a scheduling user equipment102(1), in one or more implementations, the other nodes (in the threeparty example of FIG. 1) are the transmitter user equipment 102(2) andthe receiver user equipment 102(3). As represented in FIG. 1 by“broadcast information” (labeled with circled numeral one (1)), thescheduler user equipment 102(1) broadcasts synchronization signals tosurrounding user equipments, which in this example include thetransmitter user equipment 102(2) and the receiver user equipment102(3). The broadcasting information includes the resource poolinformation. Other nodes, including the transmitter user equipment102(2) and the receiver user equipment 102(3), synchronize with thescheduler user equipment 102(1) and receive the broadcast information.

When the transmitter user equipment 102(2) has some V2X(vehicle-to-everything) traffic data packet(s), the transmitter userequipment 102(2) sends a scheduling request to the scheduler userequipment 102(1), as represented in FIG. 1 via the dashed arrow labeledwith circled numeral two (2). The scheduling request includes thetraffic type, which can comprise V2X broadcast or multi-cast traffic,cellular traffic or V2X unicast traffic (which additionally identifiesthe designated receiver user equipment for the targeted unicasttraffic).

Upon receiving the scheduling request, the scheduler user equipment102(1) starts to schedule radio resources. In general, the scheduleruser equipment 102(1) allocates radio resources so as to avoidinterference between transmitters, in generally the same way a networknode allocates radio resources.

Further general operations are represented in FIG. 2. In one or moreimplementations, the scheduling decision (scheduling data) istransmitted as DCI (Downlink Control Information) from the scheduleruser equipment 102(1) to the transmitter user equipment 102(2) and thereceiver user equipment(s), which in the example of FIG. 1 is thereceiver user equipment 102(3). The DCI communication to the transmitteruser equipment 102(2) is represented in FIG. 2 via the dashed arrowlabeled with circled numeral 3 a (DCI_T), while the DCI communication tothe receiver user equipment 102(3) is represented in FIG. 2 via thedashed arrow labeled with circled numeral 3 b (DCI_R). The DCI mayinclude the resource allocation, modulation and coding scheme (MCS)information, precoder information, and so forth.

Upon receiving the DCI, the transmitter user equipment 102(2) is totransmit data on the allocated radio resources (e.g., time slot,frequency and so forth) while the receiver user equipment 102(3) is toreceive data on the allocated radio resources. For unicast V2X traffic,the designated receiver user equipment 102(3) is picked according to thescheduling request, in which the transmitter user equipment 102(2)identified the receiver user equipment 102(3). Unicast traffic isrepresented in FIG. 2, by the “Data” arrow labeled with circled numeralfour (4). Note that the data transmission from the transmitter userequipment 102(2) to the receiver user equipment 102(3) is “direct” inthat the data transmission is not routed or in any way needs to furtherinvolve the scheduler user equipment 102(1).

FIG. 3 shows an implementation in which broadcast (or multicast) V2Xtraffic is transmitted. As generally described with reference to FIG. 1,in FIG. 3 a transmitter user equipment 302(2) has obtained transmitscheduling data (via DCI) from a scheduler user equipment 302(1), (thedashed arrow labeled 3 a), and the receive DCI is broadcast to thesurrounding user equipments 302(3)-302(n) (the dashed arrows labeled 3ba). Based on the scheduling data, the transmitter user equipment 302(2)transmits (broadcasts) data (the arrows labeled four (4) to allsurrounding receiver user equipments 302(3)-302(n), (as well as thescheduling user equipment 302(1), acting as a receiver for the broadcasttraffic. Note that FIG. 3 generally applies to multicast traffic aswell, although as is understood the receive DCI is transmitted to anappropriate group (e.g., a proper subset, but possible the full set) ofuser equipment(s).

As generally represented in FIG. 4, for cellular data, the scheduleruser equipment 402(1) is also the receiver node; any other userequipment (e.g., the node 402(3) is not involved in a scheduled datatransmission). This is represented in FIG. 4 via the dashed arrow 3 aproviding the transmission scheduling data DCI_T to the transmitter userequipment 402(2), followed by the data transmission (arrow 4) to thescheduler user equipment 402(1) based on the scheduling data.

In one alternative, if the scheduler user equipment has IAB (IntegratedAccess and Backhaul) or mobile relay functionality, then thecommunication between the transmitter user equipment 402(2) and thescheduler user equipment 402(1) can become an access link (e.g., as usedby conventional cellular user equipments) and the data can be relayedover a backhaul link to another IAB node or donor node (e.g., a nodewith wired cellular core network connectivity). In another alternative,the link between the scheduler user equipment and the transmitter userequipment can utilize one or more Sidelink control formats and datatransmission formats.

In general, the resource pool that any scheduler user equipment canschedule (including control and data resources) is orthogonal to theresource pool of any other scheduler user equipment within a given cell(corresponding to a network based station). However, a base-station witha good interference coordination scheme can configure multiple scheduleruser equipments with overlapped resource pools. For example, a networkbase station can schedule two scheduler user equipments such that thecontrol information transmitted to their supported transmitters andreceivers can be shared in a non-interfering way, e.g., share afrequency range with different time slots. In this situation, thecontrol channel monitoring resource for each transmitter user equipmentor the receiver user equipment is the union set of all the controlresources for the full set of the scheduler user equipments in the cell.With that, transmitter user equipment(s) and/or the receiver userequipment(s) effectively can hear the resource allocation for all thescheduler user equipments. The effective broadcast area becomes thewhole cell.

The various flow diagrams exemplified herein represent operations thatcan be used to facilitate technology comprising scheduling userequipment and transmitter/receiver user equipment. As is understood, theoperations are only examples to illustrate certain actions that can betaken, and can be in different orderings from those exemplified.Moreover, other operations, more operations, or fewer operations can beperformed. Still further, at least some of the operations can beperformed generally in parallel with one another; as but onenon-limiting example, a scheduler user equipment can also be atransmitter user equipment and a receiver user equipment, includingwhile waiting for a scheduling request.

FIGS. 5-7 summarize example operations of a scheduler user equipment,beginning at operation 502 which represents receiving a networkinstruction to become a scheduler user interface, along with schedulinginformation that the scheduler user equipment can use to allocate radioresources. Note that a scheduler user equipment can be elected as alocal manager, and thus operate as a scheduler user equipment without anexplicit instruction from the network, although the scheduler userequipment does need to know what resources it can allocate to the userequipments in the scheduler user equipment's group.

Operation 504 represents broadcasting synchronization signals forsurrounding/neighboring user equipments; the broadcasting informationincludes resource pool information. Other nodes synchronize with thescheduler user equipment and receive the broadcast information.Operation 506 represents waiting for a scheduling request; note that thescheduler user equipment can be performing other tasks while waiting.

When a node wants to transmit data as a transmitter user equipment, thenode sends a scheduling request, which causes operation 506 to branch tooperation 508. As described above, the scheduling request includestraffic type information that specifies V2X broadcast or multicasttraffic, V2X unicast traffic (which also indicates the receiver node),or cellular traffic.

Operation 508 represents evaluating whether the traffic type informationspecifies cellular traffic. If so, the receiver is the scheduling userequipment (and thus need not transmit DCI to another receiver).Operation 510 represents determining the transmitter (and the receiveras itself) scheduling, and operation 512 schedules (transmits) thetransmitter scheduling data via DCI to the requesting transmitter userequipment. Operation 514 represents preparing for and receiving the datavia the allocated resources.

If at operation 508 the traffic type information does not specifycellular traffic, the scheduling process branches to operation 602 ofFIG. 6, which evaluates whether the traffic is intended for a receiveruser equipment served by another scheduler user equipment; (note thatthis applies to unicast traffic). If not, operation 604 determines thetransmitter scheduling, operation 606 schedules the transmitter userequipment via DCI, and operation 608 schedules the receiver userequipment (for unicast) or receiver user equipments (for broadcast ormulticast) via DCI. At this time the scheduling user equipment is nolonger involved in this scheduling request, and the scheduling processreturns to operation 506 of FIG. 5 to await another scheduling request.Note that although not explicitly shown, it is possible for thescheduler node to also be a receiver node and/or a transmitter node.

Returning to operation 602, the traffic generated by the transmitteruser equipment and indicated in the scheduling request to the scheduleruser equipment can be intended for another V2X receiver user equipmentthat is being served by a different scheduler user equipment. If so, theoperations exemplified in FIG. 7 can be performed.

More particularly, in one alternative, represented via operations 702and 704, if the transmitter node is directly in range of the targetreceiver node (as evaluated at operation 702), the scheduler userequipment serving the transmitter user equipment node and the otherscheduler user equipment serving the receiver user equipment node maycoordinate the resource allocation and DCIs to ensure the data can besent from the transmitter user equipment node to the receiver userequipment node as if they were in the same group (operation 704). Notethat for this alternative, the scheduler user equipment needs to know orbe able to determine which other scheduler user equipment is serving theintended receiver user equipment.

In another alternative, if the scheduler user equipment has IABfunctionality, and the scheduler user equipment is aware of which otherscheduler user equipment is serving the intended receiver user equipment(operation 706), the scheduler user equipment may forward/relay the datafrom the transmitter node to the other scheduler user equipment usingSidelink over one or more backhaul hops to the other scheduler userequipment that is serving the target receiver user equipment (operation708).

Otherwise, as represented by operation 710, another alternative is forthe scheduler user equipment to forward the data to an infrastructureIAB node, which can route the traffic across multiple hops (if needed)over backhaul/Sidelink links between IAB nodes and the other(relay/serving) scheduler user equipment that is serving the targetreceiver user equipment.

FIG. 8 is a flow diagram representing example operations of a userequipment that can transmit and/or receive data. Operation 802represents receiving the broadcast information from the scheduler userequipment and syncing up with the scheduler user equipment as describedherein.

Operation 804 represents evaluating whether the user equipment has anydata to transmit. If so, operation 806 is performed, which representstransmitting the scheduling request to the scheduler user equipment,including the traffic type information, and if unicast traffic type, thereceiver identifier information. Operation 808 represents receiving thescheduling data from the scheduler user equipment via DCI. Operation 810represents transmitting the data to the one or more receiver userequipment(s) based on the transmit scheduling data received at operation808.

Whether or not the user equipment has any data to transmit, the user maybe scheduled for receiving data, as evaluated at operation 812. If so,operation 814 represents preparing for/receiving the data on theallocated receiver radio resources (based on the receiver schedulingdata).

FIG. 9 represents general, example operations of a scheduler userequipment 112, e.g., 112(1) (FIG. 1). Operation 902 representsbroadcasting, by a scheduler user equipment comprising a processor,synchronization signals to a first user equipment that identify thescheduler user equipment as capable of scheduling resources. Operation904 represents receiving, by the scheduler user equipment from the firstuser equipment, a scheduling request for the scheduling of the resourcesfor transmission of data by the first user equipment. In response to thereceiving the scheduling request for the scheduling of the resources,operation 906 represents facilitating, by the scheduler user equipment,transmitting scheduling information to the first user equipment tofurther facilitate the transmission of the data by the first userequipment.

Transmitting the scheduling information to the first user equipment cancomprise transmitting the scheduling information as downlink controlinformation to the first user equipment.

Aspects can comprise, facilitating, by the scheduler user equipment,transmitting the scheduling information to a second user equipment tofacilitate the transmission of the data by the first user equipmentdirectly to the second user equipment.

Receiving the scheduling request can comprise receiving traffic typeinformation identifying the scheduling request as corresponding tounicast traffic; aspects can comprise, receiving, by the scheduler userequipment from the first user equipment, an identifier of the seconduser equipment. Receiving the scheduling request can comprise receivingtraffic type information identifying the scheduling request ascorresponding to broadcast traffic. Receiving the scheduling request cancomprise receiving traffic type information identifying the schedulingrequest as corresponding to multicast traffic. Receiving the schedulingrequest can comprise receiving traffic type information identifying thescheduling request as corresponding to cellular traffic.

Aspects can comprise operating the scheduler user equipment as an accesslink with respect to the first node, comprising receiving, by thescheduler user equipment, cellular data from the first node, andrelaying, by the scheduler user equipment, the cellular data to anetwork device.

Aspects can comprise, communicating, by the scheduler user equipment,with the first user equipment using one or more Sidelink control formatsand one or more Sidelink data transmission formats to receive cellulardata from the first user equipment.

The scheduler user equipment can comprise a first scheduler userequipment communicatively coupled to a network device associated with acell. Aspects can comprise receiving, by the first scheduler userequipment from the network device, first resource pool information withwhich the first scheduler user equipment is configured for transmissionof the scheduling information to the first user equipment, wherein thefirst resource pool information overlaps, without causing communicationinterference in the cell, with second resource pool information of asecond scheduler user equipment communicatively coupled to the networkdevice associated with the cell.

The scheduler user equipment can comprise a first scheduler userequipment communicatively coupled to a network device. Aspects cancomprise, receiving, from the first user equipment, an identifier of asecond user equipment identifying the second user equipment as anintended recipient of the transmission of the data by the first userequipment, determining, by the first scheduler user equipment, that thesecond user equipment is served by a second scheduler user equipment,and forwarding, by the first scheduler user equipment, a transmissionreceived by the first scheduler user equipment from the first userequipment to the second scheduler user equipment for communication tothe second user equipment.

FIG. 10 represents general, example operations of a transmitting radiouser equipment device 112 (e.g., 112(2) of FIG. 2), generally comprisinga processor a memory that stores executable instructions that, whenexecuted by the processor, facilitate performance of operations. Exampleoperations can comprise requesting scheduling of resources from ascheduler user equipment device that is configured with resourcescheduling capability (operation 1002), and in response to therequesting the scheduling of the resources, receiving scheduling datafrom the scheduler user equipment device (operation 1004). Operation1006 represents communicating directly with a receiver user equipmentdevice based on the scheduling data.

Requesting the scheduling of the resources can comprise requesting thescheduling data for a broadcast transmission, and communicating directlywith the receiver user equipment device based on the scheduling data cancomprise broadcasting a transmission to the receiver user equipmentdevice.

Requesting the scheduling of the resources can comprise requesting thescheduling data for a multicast transmission, and communicating directlywith the receiver user equipment device based on the scheduling data cancomprise multicasting a transmission to the receiver user equipmentdevice.

Requesting the scheduling of the resources can comprise requesting thescheduling data for a unicast transmission to the receiver userequipment device and identifying the receiver user equipment device tothe scheduler user equipment device, and communicating directly with thereceiver user equipment device based on the scheduling data can compriseunicasting a transmission to the receiver user equipment device.

Requesting the scheduling of the resources can comprise requesting thescheduling data for transmission of cellular data to the scheduler userequipment device.

FIG. 11 represents general, example operations of a radio user equipmentdevice, e.g., operating as a scheduler radio user equipment device.Example operations can comprise receiving, from a network device coupledto the local manager radio user equipment, radio user equipmentcommunication resource scheduling data (operation 1102) and receiving,from a transmitter user equipment that is in a group managed by thelocal manager radio user equipment, a request to schedule thetransmitter user equipment with scheduling information, wherein therequest is associated with traffic type information (operation 1104).Operation 1106 represents scheduling the transmitter user equipmentbased on the radio user equipment communication resource scheduling dataand the traffic type information, to facilitate a transmission of datafrom the transmitter user equipment to a receiver user equipment.

The traffic type information can correspond to cellular datainformation, and wherein the operations further comprise, receiving thetransmission comprising cellular data from the transmitter userequipment at the local manager radio user equipment, and relaying thecellular data to the network device.

The traffic type information can correspond to unicast information, andwherein the operations further comprise, receiving an identifier of thereceiver user equipment, and scheduling the receiver user equipmentbased on the radio user equipment communication resource scheduling dataand the traffic type information, to facilitate a direct transmission ofthe data from the transmitter user equipment to the receiver userequipment.

The receiver user equipment can be in a different group managed by adifferent local manager radio user equipment, and the operations canfurther comprise coordinating with the different local manager radiouser equipment to facilitate the transmission of the data from thetransmitter user equipment to the receiver user equipment.

As can be seen, this three-party communication allows a dedicated node(a scheduler user equipment) to coordinate the resource utilization in acertain local area. The scheduler user equipment operating as adedicated resource coordinator can coordinate the resource utilizationto avoid frequent resource usage collisions, thereby improve theefficiency of communications. Moreover, because there is no need for acomprehensive initial access procedure the transmitter user equipmentand the receive user equipment do not need a formal association with thescheduler user equipment. When the transmitter user equipment and/or thereceive user equipment move away from the scheduler user equipment,there is no need for a handover procedure.

This technology described herein facilitates hardware sharing betweenthe regular cellular network and the vehicle-to-everything (V2X) ordevice-to-device (D2D) network. The same node (scheduler user equipment)can serve as a relay node for the cellular network as well asvehicle-to-everything local manager. This technology described hereinfacilitates the use of mobile relays with existing infrastructure-basedIAB nodes under a common architecture and resource allocation framework.This technology described herein facilitates spectrum sharing betweenregular cellular networks and V2X services; the same spectrum band maybe reused by V2X service or regular cellular traffic.

Referring now to FIG. 12, illustrated is an example block diagram of anexample mobile handset 1200 operable to engage in a system architecturethat facilitates wireless communications according to one or moreembodiments described herein. Although a mobile handset is illustratedherein, it will be understood that other devices can be a mobile device,and that the mobile handset is merely illustrated to provide context forthe embodiments of the various embodiments described herein. Thefollowing discussion is intended to provide a brief, general descriptionof an example of a suitable environment in which the various embodimentscan be implemented. While the description includes a general context ofcomputer-executable instructions embodied on a machine-readable storagemedium, those skilled in the art will recognize that the innovation alsocan be implemented in combination with other program modules and/or as acombination of hardware and software.

Generally, applications (e.g., program modules) can include routines,programs, components, data structures, etc., that perform particulartasks or implement particular abstract data types. Moreover, thoseskilled in the art will appreciate that the methods described herein canbe practiced with other system configurations, includingsingle-processor or multiprocessor systems, minicomputers, mainframecomputers, as well as personal computers, hand-held computing devices,microprocessor-based or programmable consumer electronics, and the like,each of which can be operatively coupled to one or more associateddevices

A computing device can typically include a variety of machine-readablemedia. Machine-readable media can be any available media that can beaccessed by the computer and includes both volatile and non-volatilemedia, removable and non-removable media. By way of example and notlimitation, computer-readable media can comprise computer storage mediaand communication media. Computer storage media can include volatileand/or non-volatile media, removable and/or non-removable mediaimplemented in any method or technology for storage of information, suchas computer-readable instructions, data structures, program modules, orother data. Computer storage media can include, but is not limited to,RAM, ROM, EEPROM, flash memory or other memory technology, solid statedrive (SSD) or other solid-state storage technology, Compact Disk ReadOnly Memory (CD ROM), digital video disk (DVD), Blu-ray disk, or otheroptical disk storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other medium which canbe used to store the desired information and which can be accessed bythe computer. In this regard, the terms “tangible” or “non-transitory”herein as applied to storage, memory or computer-readable media, are tobe understood to exclude only propagating transitory signals per se asmodifiers and do not relinquish rights to all standard storage, memoryor computer-readable media that are not only propagating transitorysignals per se.

Communication media typically embodies computer-readable instructions,data structures, program modules, or other data in a modulated datasignal such as a carrier wave or other transport mechanism, and includesany information delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media includes wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless media. Combinations of the anyof the above should also be included within the scope ofcomputer-readable media

The handset includes a processor 1202 for controlling and processing allonboard operations and functions. A memory 1204 interfaces to theprocessor 1202 for storage of data and one or more applications 1206(e.g., a video player software, user feedback component software, etc.).Other applications can include voice recognition of predetermined voicecommands that facilitate initiation of the user feedback signals. Theapplications 1206 can be stored in the memory 1204 and/or in a firmware1208, and executed by the processor 1202 from either or both the memory1204 or/and the firmware 1208. The firmware 1208 can also store startupcode for execution in initializing the handset 1200. A communicationscomponent 1210 interfaces to the processor 1202 to facilitatewired/wireless communication with external systems, e.g., cellularnetworks, VoIP networks, and so on. Here, the communications component1210 can also include a suitable cellular transceiver 1211 (e.g., a GSMtransceiver) and/or an unlicensed transceiver 1213 (e.g., Wi-Fi, WiMax)for corresponding signal communications. The handset 1200 can be adevice such as a cellular telephone, a PDA with mobile communicationscapabilities, and messaging-centric devices. The communicationscomponent 1210 also facilitates communications reception fromterrestrial radio networks (e.g., broadcast), digital satellite radionetworks, and Internet-based radio services networks

The handset 1200 includes a display 1212 for displaying text, images,video, telephony functions (e.g., a Caller ID function), setupfunctions, and for user input. For example, the display 1212 can also bereferred to as a “screen” that can accommodate the presentation ofmultimedia content (e.g., music metadata, messages, wallpaper, graphics,etc.). The display 1212 can also display videos and can facilitate thegeneration, editing and sharing of video quotes. A serial I/O interface1214 is provided in communication with the processor 1202 to facilitatewired and/or wireless serial communications (e.g., USB, and/or IEEE1294) through a hardwire connection, and other serial input devices(e.g., a keyboard, keypad, and mouse). This supports updating andtroubleshooting the handset 1200, for example. Audio capabilities areprovided with an audio I/O component 1216, which can include a speakerfor the output of audio signals related to, for example, indication thatthe user pressed the proper key or key combination to initiate the userfeedback signal. The audio I/O component 1216 also facilitates the inputof audio signals through a microphone to record data and/or telephonyvoice data, and for inputting voice signals for telephone conversations.

The handset 1200 can include a slot interface 1218 for accommodating aSIC (Subscriber Identity Component) in the form factor of a cardSubscriber Identity Module (SIM) or universal SIM 1220, and interfacingthe SIM card 1220 with the processor 1202. However, it is to beappreciated that the SIM card 1220 can be manufactured into the handset1200, and updated by downloading data and software.

The handset 1200 can process IP data traffic through the communicationscomponent 1210 to accommodate IP traffic from an IP network such as, forexample, the Internet, a corporate intranet, a home network, a personarea network, etc., through an ISP or broadband cable provider. Thus,VoIP traffic can be utilized by the handset 1200 and IP-based multimediacontent can be received in either an encoded or a decoded format.

A video processing component 1222 (e.g., a camera) can be provided fordecoding encoded multimedia content. The video processing component 1222can aid in facilitating the generation, editing, and sharing of videoquotes. The handset 1200 also includes a power source 1224 in the formof batteries and/or an AC power subsystem, which power source 1224 caninterface to an external power system or charging equipment (not shown)by a power I/O component 1226.

The handset 1200 can also include a video component 1230 for processingvideo content received and, for recording and transmitting videocontent. For example, the video component 1230 can facilitate thegeneration, editing and sharing of video quotes. A location trackingcomponent 1232 facilitates geographically locating the handset 1200. Asdescribed hereinabove, this can occur when the user initiates thefeedback signal automatically or manually. A user input component 1234facilitates the user initiating the quality feedback signal. The userinput component 1234 can also facilitate the generation, editing andsharing of video quotes. The user input component 1234 can include suchconventional input device technologies such as a keypad, keyboard,mouse, stylus pen, and/or touch screen, for example.

Referring again to the applications 1206, a hysteresis component 1236facilitates the analysis and processing of hysteresis data, which isutilized to determine when to associate with the access point. Asoftware trigger component 1238 can be provided that facilitatestriggering of the hysteresis component 1236 when the Wi-Fi transceiver1213 detects the beacon of the access point. A SIP client 1240 enablesthe handset 1200 to support SIP protocols and register the subscriberwith the SIP registrar server. The applications 1206 can also include aclient 1242 that provides at least the capability of discovery, play andstore of multimedia content, for example, music.

The handset 1200, as indicated above related to the communicationscomponent 1210, includes an indoor network radio transceiver 1213 (e.g.,Wi-Fi transceiver). This function supports the indoor radio link, suchas IEEE 802.11, for the dual-mode GSM handset 1200. The handset 1200 canaccommodate at least satellite radio services through a handset that cancombine wireless voice and digital radio chipsets into a single handhelddevice.

Referring now to FIG. 13, illustrated is an example block diagram of anexample computer 1300 operable to engage in a system architecture thatfacilitates wireless communications according to one or more embodimentsdescribed herein. The computer 1300 can provide networking andcommunication capabilities between a wired or wireless communicationnetwork and a server (e.g., Microsoft server) and/or communicationdevice. In order to provide additional context for various aspectsthereof, FIG. 13 and the following discussion are intended to provide abrief, general description of a suitable computing environment in whichthe various aspects of the innovation can be implemented to facilitatethe establishment of a transaction between an entity and a third party.While the description above is in the general context ofcomputer-executable instructions that can run on one or more computers,those skilled in the art will recognize that the innovation also can beimplemented in combination with other program modules and/or as acombination of hardware and software.

Generally, program modules include routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will appreciatethat the inventive methods can be practiced with other computer systemconfigurations, including single-processor or multiprocessor computersystems, minicomputers, mainframe computers, as well as personalcomputers, hand-held computing devices, microprocessor-based orprogrammable consumer electronics, and the like, each of which can beoperatively coupled to one or more associated devices.

The illustrated aspects of the innovation can also be practiced indistributed computing environments where certain tasks are performed byremote processing devices that are linked through a communicationsnetwork. In a distributed computing environment, program modules can belocated in both local and remote memory storage devices.

Computing devices typically include a variety of media, which caninclude computer-readable storage media or communications media, whichtwo terms are used herein differently from one another as follows.

Computer-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media can include,but are not limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disk (DVD) or other optical diskstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or other tangible and/or non-transitorymedia which can be used to store desired information. Computer-readablestorage media can be accessed by one or more local or remote computingdevices, e.g., via access requests, queries or other data retrievalprotocols, for a variety of operations with respect to the informationstored by the medium.

Communications media can embody computer-readable instructions, datastructures, program modules, or other structured or unstructured data ina data signal such as a modulated data signal, e.g., a carrier wave orother transport mechanism, and includes any information delivery ortransport media. The term “modulated data signal” or signals refers to asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in one or more signals. By way ofexample, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

The techniques described herein can be applied to any device or set ofdevices (machines) capable of running programs and processes. It can beunderstood, therefore, that servers including physical and/or virtualmachines, personal computers, laptops, handheld, portable and othercomputing devices and computing objects of all kinds including cellphones, tablet/slate computers, gaming/entertainment consoles and thelike are contemplated for use in connection with various implementationsincluding those exemplified herein. Accordingly, the general purposecomputing mechanism described below with reference to FIG. 13 is but oneexample of a computing device.

In order to provide a context for the various aspects of the disclosedsubject matter, FIG. 13 and the following discussion, are intended toprovide a brief, general description of a suitable environment in whichthe various aspects of the disclosed subject matter can be implemented.While the subject matter has been described above in the general contextof computer-executable instructions of a computer program that runs on acomputer and/or computers, those skilled in the art will recognize thatthe disclosed subject matter also can be implemented in combination withother program modules. Generally, program modules include routines,programs, components, data structures, etc. that perform particulartasks and/or implement particular abstract data types.

In the subject specification, terms such as “store,” “storage,” “datastore,” data storage,” “database,” and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It will be appreciatedthat the memory components described herein can be either volatilememory or nonvolatile memory, or can include both volatile andnonvolatile memory, by way of illustration, and not limitation, volatilememory 1320 (see below), non-volatile memory 1322 (see below), diskstorage 1324 (see below), and memory storage 1346 (see below). Further,nonvolatile memory can be included in read only memory (ROM),programmable ROM (PROM), electrically programmable ROM (EPROM),electrically erasable ROM (EEPROM), or flash memory. Volatile memory caninclude random access memory (RAM), which acts as external cache memory.By way of illustration and not limitation, RAM is available in manyforms such as synchronous RAM (SRAM), dynamic RAM (DRAM), synchronousDRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM(ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM (DRRAM).Additionally, the disclosed memory components of systems or methodsherein are intended to comprise, without being limited to comprising,these and any other suitable types of memory.

Moreover, it will be noted that the disclosed subject matter can bepracticed with other computer system configurations, includingsingle-processor or multiprocessor computer systems, mini-computingdevices, mainframe computers, as well as personal computers, hand-heldcomputing devices (e.g., PDA, phone, watch, tablet computers, netbookcomputers, . . . ), microprocessor-based or programmable consumer orindustrial electronics, and the like. The illustrated aspects can alsobe practiced in distributed computing environments where tasks areperformed by remote processing devices that are linked through acommunications network; however, some if not all aspects of the subjectdisclosure can be practiced on stand-alone computers. In a distributedcomputing environment, program modules can be located in both local andremote memory storage devices.

FIG. 13 illustrates a block diagram of a computing system 1300 operableto execute the disclosed systems and methods in accordance with anembodiment. Computer 1312, which can be, for example, part of thehardware of system 1320, includes a processing unit 1314, a systemmemory 1316, and a system bus 1318. System bus 1318 couples systemcomponents including, but not limited to, system memory 1316 toprocessing unit 1314. Processing unit 1314 can be any of variousavailable processors. Dual microprocessors and other multiprocessorarchitectures also can be employed as processing unit 1314.

System bus 1318 can be any of several types of bus structure(s)including a memory bus or a memory controller, a peripheral bus or anexternal bus, and/or a local bus using any variety of available busarchitectures including, but not limited to, Industrial StandardArchitecture (ISA), Micro-Channel Architecture (MSA), Extended ISA(EISA), Intelligent Drive Electronics, VESA Local Bus (VLB), PeripheralComponent Interconnect (PCI), Card Bus, Universal Serial Bus (USB),Advanced Graphics Port (AGP), Personal Computer Memory CardInternational Association bus (PCMCIA), Firewire (IEEE 1394), and SmallComputer Systems Interface (SCSI).

System memory 1316 can include volatile memory 1320 and nonvolatilememory 1322. A basic input/output system (BIOS), containing routines totransfer information between elements within computer 1312, such asduring start-up, can be stored in nonvolatile memory 1322. By way ofillustration, and not limitation, nonvolatile memory 1322 can includeROM, PROM, EPROM, EEPROM, or flash memory. Volatile memory 1320 includesRAM, which acts as external cache memory. By way of illustration and notlimitation, RAM is available in many forms such as SRAM, dynamic RAM(DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM),enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), Rambus direct RAM(RDRAM), direct Rambus dynamic RAM (DRDRAM), and Rambus dynamic RAM(RDRAM).

Computer 1312 can also include removable/non-removable,volatile/non-volatile computer storage media. FIG. 13 illustrates, forexample, disk storage 1324. Disk storage 1324 includes, but is notlimited to, devices like a magnetic disk drive, floppy disk drive, tapedrive, flash memory card, or memory stick. In addition, disk storage1324 can include storage media separately or in combination with otherstorage media including, but not limited to, an optical disk drive suchas a compact disk ROM device (CD-ROM), CD recordable drive (CD-R Drive),CD rewritable drive (CD-RW Drive) or a digital versatile disk ROM drive(DVD-ROM). To facilitate connection of the disk storage devices 1324 tosystem bus 1318, a removable or non-removable interface is typicallyused, such as interface 1326.

Computing devices typically include a variety of media, which caninclude computer-readable storage media or communications media, whichtwo terms are used herein differently from one another as follows.

Computer-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media can include,but are not limited to, random access memory (RAM), read only memory(ROM), electrically erasable programmable read only memory (EEPROM),flash memory or other memory technology, solid state drive (SSD) orother solid-state storage technology, compact disk read only memory (CDROM), digital versatile disk (DVD), Blu-ray disc or other optical diskstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices or other tangible and/or non-transitorymedia which can be used to store desired information. In this regard,the terms “tangible” or “non-transitory” herein as applied to storage,memory or computer-readable media, are to be understood to exclude onlypropagating transitory signals per se as modifiers and do not relinquishrights to all standard storage, memory or computer-readable media thatare not only propagating transitory signals per se. In an aspect,tangible media can include non-transitory media wherein the term“non-transitory” herein as may be applied to storage, memory orcomputer-readable media, is to be understood to exclude only propagatingtransitory signals per se as a modifier and does not relinquish coverageof all standard storage, memory or computer-readable media that are notonly propagating transitory signals per se. For the avoidance of doubt,the term “computer-readable storage device” is used and defined hereinto exclude transitory media. Computer-readable storage media can beaccessed by one or more local or remote computing devices, e.g., viaaccess requests, queries or other data retrieval protocols, for avariety of operations with respect to the information stored by themedium.

Communications media typically embody computer-readable instructions,data structures, program modules or other structured or unstructureddata in a data signal such as a modulated data signal, e.g., a carrierwave or other transport mechanism, and includes any information deliveryor transport media. The term “modulated data signal” or signals refersto a signal that has one or more of its characteristics set or changedin such a manner as to encode information in one or more signals. By wayof example, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

It can be noted that FIG. 13 describes software that acts as anintermediary between users and computer resources described in suitableoperating environment 1300. Such software includes an operating system1328. Operating system 1328, which can be stored on disk storage 1324,acts to control and allocate resources of computer system 1312. Systemapplications 1330 take advantage of the management of resources byoperating system 1328 through program modules 1332 and program data 1334stored either in system memory 1316 or on disk storage 1324. It is to benoted that the disclosed subject matter can be implemented with variousoperating systems or combinations of operating systems.

A user can enter commands or information into computer 1312 throughinput device(s) 1336. As an example, a mobile device and/or portabledevice can include a user interface embodied in a touch sensitivedisplay panel allowing a user to interact with computer 1312. Inputdevices 1336 include, but are not limited to, a pointing device such asa mouse, trackball, stylus, touch pad, keyboard, microphone, joystick,game pad, satellite dish, scanner, TV tuner card, digital camera,digital video camera, web camera, cell phone, smartphone, tabletcomputer, etc. These and other input devices connect to processing unit1314 through system bus 1318 by way of interface port(s) 1338. Interfaceport(s) 1338 include, for example, a serial port, a parallel port, agame port, a universal serial bus (USB), an infrared port, a Bluetoothport, an IP port, or a logical port associated with a wireless service,etc. Output device(s) 1340 and a move use some of the same type of portsas input device(s) 1336.

Thus, for example, a USB port can be used to provide input to computer1312 and to output information from computer 1312 to an output device1340. Output adapter 1342 is provided to illustrate that there are someoutput devices 1340 like monitors, speakers, and printers, among otheroutput devices 1340, which use special adapters. Output adapters 1342include, by way of illustration and not limitation, video and soundcards that provide means of connection between output device 1340 andsystem bus 1318. It should be noted that other devices and/or systems ofdevices provide both input and output capabilities such as remotecomputer(s) 1344.

Computer 1312 can operate in a networked environment using logicalconnections to one or more remote computers, such as remote computer(s)1344. Remote computer(s) 1344 can be a personal computer, a server, arouter, a network PC, cloud storage, cloud service, a workstation, amicroprocessor based appliance, a peer device, or other common networknode and the like, and typically includes many or all of the elementsdescribed relative to computer 1312.

For purposes of brevity, only a memory storage device 1346 isillustrated with remote computer(s) 1344. Remote computer(s) 1344 islogically connected to computer 1312 through a network interface 1348and then physically connected by way of communication connection 1350.Network interface 1348 encompasses wire and/or wireless communicationnetworks such as local-area networks (LAN) and wide-area networks (WAN).LAN technologies include Fiber Distributed Data Interface (FDDI), CopperDistributed Data Interface (CDDI), Ethernet, Token Ring and the like.WAN technologies include, but are not limited to, point-to-point links,circuit-switching networks like Integrated Services Digital Networks(ISDN) and variations thereon, packet switching networks, and DigitalSubscriber Lines (DSL). As noted below, wireless technologies may beused in addition to or in place of the foregoing.

Communication connection(s) 1350 refer(s) to hardware/software employedto connect network interface 1348 to bus 1318. While communicationconnection 1350 is shown for illustrative clarity inside computer 1312,it can also be external to computer 1312. The hardware/software forconnection to network interface 1348 can include, for example, internaland external technologies such as modems, including regular telephonegrade modems, cable modems and DSL modems, ISDN adapters, and Ethernetcards.

The above description of illustrated embodiments of the subjectdisclosure, including what is described in the Abstract, is not intendedto be exhaustive or to limit the disclosed embodiments to the preciseforms disclosed. While specific embodiments and examples are describedherein for illustrative purposes, various modifications are possiblethat are considered within the scope of such embodiments and examples,as those skilled in the relevant art can recognize.

In this regard, while the disclosed subject matter has been described inconnection with various embodiments and corresponding Figures, whereapplicable, it is to be understood that other similar embodiments can beused or modifications and additions can be made to the describedembodiments for performing the same, similar, alternative, or substitutefunction of the disclosed subject matter without deviating therefrom.Therefore, the disclosed subject matter should not be limited to anysingle embodiment described herein, but rather should be construed inbreadth and scope in accordance with the appended claims below.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. Processors can exploit nano-scale architectures suchas, but not limited to, molecular and quantum-dot based transistors,switches and gates, in order to optimize space usage or enhanceperformance of user equipment. A processor may also be implemented as acombination of computing processing units.

In the subject specification, terms such as “store,” “storage,” “datastore,” data storage,” “database,” and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It will be appreciatedthat the memory components described herein can be either volatilememory or nonvolatile memory, or can include both volatile andnonvolatile memory.

As used in this application, the terms “component,” “system,”“platform,” “layer,” “selector,” “interface,” and the like are intendedto refer to a computer-related entity or an entity related to anoperational apparatus with one or more specific functionalities, whereinthe entity can be either hardware, a combination of hardware andsoftware, software, or software in execution. As an example, a componentmay be, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration and not limitation, both anapplication running on a server and the server can be a component. Oneor more components may reside within a process and/or thread ofexecution and a component may be localized on one computer and/ordistributed between two or more computers. In addition, these componentscan execute from various computer readable media, device readablestorage devices, or machine readable media having various datastructures stored thereon. The components may communicate via localand/or remote processes such as in accordance with a signal having oneor more data packets (e.g., data from one component interacting withanother component in a local system, distributed system, and/or across anetwork such as the Internet with other systems via the signal). Asanother example, a component can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry, which is operated by a software or firmwareapplication executed by a processor, wherein the processor can beinternal or external to the apparatus and executes at least a part ofthe software or firmware application. As yet another example, acomponent can be an apparatus that provides specific functionalitythrough electronic components without mechanical parts, the electroniccomponents can include a processor therein to execute software orfirmware that confers at least in part the functionality of theelectronic components.

In addition, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom context, “X employs A or B” is intended to mean any of the naturalinclusive permutations. That is, if X employs A; X employs B; or Xemploys both A and B, then “X employs A or B” is satisfied under any ofthe foregoing instances. Moreover, articles “a” and “an” as used in thesubject specification and annexed drawings should generally be construedto mean “one or more” unless specified otherwise or clear from contextto be directed to a singular form.

Moreover, terms like “user equipment (UE),” “mobile station,” “mobile,”subscriber station,” “subscriber equipment,” “access terminal,”“terminal,” “handset,” and similar terminology, refer to a wirelessdevice utilized by a subscriber or user of a wireless communicationservice to receive or convey data, control, voice, video, sound, gaming,or substantially any data-stream or signaling-stream. The foregoingterms are utilized interchangeably in the subject specification andrelated drawings. Likewise, the terms “access point (AP),” “basestation,” “NodeB,” “evolved Node B (eNodeB),” “home Node B (HNB),” “homeaccess point (HAP),” “cell device,” “sector,” “cell,” and the like, areutilized interchangeably in the subject application, and refer to awireless network component or appliance that serves and receives data,control, voice, video, sound, gaming, or substantially any data-streamor signaling-stream to and from a set of subscriber stations or providerenabled devices. Data and signaling streams can include packetized orframe-based flows.

Additionally, the terms “core-network”, “core”, “core carrier network”,“carrier-side”, or similar terms can refer to components of atelecommunications network that typically provides some or all ofaggregation, authentication, call control and switching, charging,service invocation, or gateways. Aggregation can refer to the highestlevel of aggregation in a service provider network wherein the nextlevel in the hierarchy under the core nodes is the distribution networksand then the edge networks. User equipments do not normally connectdirectly to the core networks of a large service provider but can berouted to the core by way of a switch or radio area network.Authentication can refer to determinations regarding whether the userrequesting a service from the telecom network is authorized to do sowithin this network or not. Call control and switching can referdeterminations related to the future course of a call stream acrosscarrier equipment based on the call signal processing. Charging can berelated to the collation and processing of charging data generated byvarious network nodes. Two common types of charging mechanisms found inpresent day networks can be prepaid charging and postpaid charging.Service invocation can occur based on some explicit action (e.g. calltransfer) or implicitly (e.g., call waiting). It is to be noted thatservice “execution” may or may not be a core network functionality asthird party network/nodes may take part in actual service execution. Agateway can be present in the core network to access other networks.Gateway functionality can be dependent on the type of the interface withanother network.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,”“prosumer,” “agent,” and the like are employed interchangeablythroughout the subject specification, unless context warrants particulardistinction(s) among the terms. It should be appreciated that such termscan refer to human entities or automated components (e.g., supportedthrough artificial intelligence, as through a capacity to makeinferences based on complex mathematical formalisms), that can providesimulated vision, sound recognition and so forth.

Aspects, features, or advantages of the subject matter can be exploitedin substantially any, or any, wired, broadcast, wirelesstelecommunication, radio technology or network, or combinations thereof.Non-limiting examples of such technologies or networks include Geocasttechnology; broadcast technologies (e.g., sub-Hz, ELF, VLF, LF, MF, HF,VHF, UHF, SHF, THz broadcasts, etc.); Ethernet; X.25; powerline-typenetworking (e.g., PowerLine AV Ethernet, etc.); femto-cell technology;Wi-Fi; Worldwide Interoperability for Microwave Access (WiMAX); EnhancedGeneral Packet Radio Service (Enhanced GPRS); Third GenerationPartnership Project (3GPP or 3G) Long Term Evolution (LTE); 3GPPUniversal Mobile Telecommunications System (UMTS) or 3GPP UMTS; ThirdGeneration Partnership Project 2 (3GPP2) Ultra Mobile Broadband (UMB);High Speed Packet Access (HSPA); High Speed Downlink Packet Access(HSDPA); High Speed Uplink Packet Access (HSUPA); GSM Enhanced DataRates for GSM Evolution (EDGE) Radio Access Network (RAN) or GERAN; UMTSTerrestrial Radio Access Network (UTRAN); or LTE Advanced.

What has been described above includes examples of systems and methodsillustrative of the disclosed subject matter. It is, of course, notpossible to describe every combination of components or methods herein.One of ordinary skill in the art may recognize that many furthercombinations and permutations of the disclosure are possible.Furthermore, to the extent that the terms “includes,” “has,”“possesses,” and the like are used in the detailed description, claims,appendices and drawings such terms are intended to be inclusive in amanner similar to the term “comprising” as “comprising” is interpretedwhen employed as a transitional word in a claim.

While the various embodiments are susceptible to various modificationsand alternative constructions, certain illustrated implementationsthereof are shown in the drawings and have been described above indetail. It should be understood, however, that there is no intention tolimit the various embodiments to the specific forms disclosed, but onthe contrary, the intention is to cover all modifications, alternativeconstructions, and equivalents falling within the spirit and scope ofthe various embodiments.

In addition to the various implementations described herein, it is to beunderstood that other similar implementations can be used ormodifications and additions can be made to the describedimplementation(s) for performing the same or equivalent function of thecorresponding implementation(s) without deviating therefrom. Stillfurther, multiple processing chips or multiple devices can share theperformance of one or more functions described herein, and similarly,storage can be effected across a plurality of devices. Accordingly, theinvention is not to be limited to any single implementation, but ratheris to be construed in breadth, spirit and scope in accordance with theappended claims.

What is claimed is:
 1. A method, comprising: broadcasting, by ascheduler user equipment comprising a processor, synchronization signalsto a first user equipment that identify the scheduler user equipment ascapable of scheduling resources, wherein the scheduler user equipmentcomprises a first scheduler user equipment communicatively coupled to anetwork device associated with a cell; receiving, by the first scheduleruser equipment from the network device, first resource pool informationwith which the first scheduler user equipment is configured fortransmission of the scheduling information to the first user equipment,wherein the first resource pool information overlaps, without causingcommunication interference in the cell, with second resource poolinformation of a second scheduler user equipment communicatively coupledto the network device associated with the cell; receiving, by thescheduler user equipment from the first user equipment, a schedulingrequest for the scheduling of the resources for transmission of data bythe first user equipment; and in response to the receiving thescheduling request for the scheduling of the resources, facilitating, bythe scheduler user equipment, transmitting scheduling information to thefirst user equipment and transmitting scheduling information to a seconduser equipment, to further facilitate the transmission of the data bythe first user equipment directly to the second user equipment.
 2. Themethod of claim 1, wherein the transmitting the scheduling informationto the first user equipment comprises transmitting the schedulinginformation as downlink control information to the first user equipment.3. The method of claim 1, wherein the receiving the scheduling requestfurther comprises receiving traffic type information identifying thescheduling request as corresponding to unicast traffic, and furthercomprising, receiving, by the scheduler user equipment from the firstuser equipment, an identifier of the second user equipment.
 4. Themethod of claim 1, wherein the receiving the scheduling request furthercomprises receiving traffic type information identifying the schedulingrequest as corresponding to broadcast traffic, and wherein in responseto the receiving the scheduling request for the scheduling of theresources, the facilitating, by the scheduler user equipment furthercomprises, facilitating, by the scheduler user equipment, transmittingthe scheduling information to a third user equipment to facilitate thetransmission of the data as a broadcast transmission by the first userequipment to the second user equipment and third user equipment.
 5. Themethod of claim 1, wherein the receiving the scheduling request furthercomprises receiving traffic type information identifying the schedulingrequest as corresponding to multicast traffic, and wherein in responseto the receiving the scheduling request for the scheduling of theresources, the facilitating, by the scheduler user equipment furthercomprises, facilitating, by the scheduler user equipment, transmittingthe scheduling information to a third user equipment to facilitate thetransmission of the data as a multicast transmission by the first userequipment to the second user equipment and third user equipment.
 6. Themethod of claim 1, wherein the receiving the scheduling request furthercomprises receiving traffic type information identifying the schedulingrequest as corresponding to cellular traffic.
 7. The method of claim 6,further comprising operating the scheduler user equipment as an accesslink with respect to the first user equipment, comprising receiving, bythe scheduler user equipment, cellular data from the first userequipment, and relaying, by the scheduler user equipment, the cellulardata to a network device.
 8. The method of claim 6, further comprising,communicating, by the scheduler user equipment, with the first userequipment using one or more Sidelink control formats and one or moreSidelink data transmission formats to receive cellular data from thefirst user equipment.
 9. The method of claim 1, wherein the scheduleruser equipment comprises the first scheduler user equipmentcommunicatively coupled to the network device, and further comprising,receiving, from the first user equipment, an identifier of a third userequipment identifying the third user equipment as an intended recipientof the transmission of the data by the first user equipment,determining, by the first scheduler user equipment, that the third userequipment is served by the second scheduler user equipment, andforwarding, by the first scheduler user equipment, a transmissionreceived by the first scheduler user equipment from the first userequipment to the second scheduler user equipment for communication tothe third user equipment.
 10. The method of claim 1, wherein thescheduler user equipment comprises the first scheduler user equipmentcommunicatively coupled to the network device, and further comprising,receiving, from the first user equipment, an identifier of the seconduser equipment identifying the second user equipment as an intendedrecipient of the transmission of the data by the first user equipment,determining, by the first scheduler user equipment, that the second userequipment is served by the second scheduler user equipment, andcoordinating, by the first scheduler user equipment and the secondscheduler user equipment, to facilitate direct communication from thefirst user equipment to the second user equipment.
 11. A transmitteruser equipment device, comprising: a processor; and a memory that storesexecutable instructions that, when executed by the processor, facilitateperformance of operations, the operations comprising: requestingscheduling of resources from a scheduler user equipment device that isconfigured with resource scheduling capability; in response to therequesting the scheduling of the resources, receiving scheduling datafrom the scheduler user equipment device; and communicating directlywith a receiver user equipment device based on the scheduling data,wherein the communicating comprises, in response to determining that therequesting the scheduling of the resources comprises requesting thescheduling data for a broadcast transmission, broadcasting atransmission to the receiver user equipment device.
 12. The transmitteruser equipment device of claim 11, wherein the communicating comprises,in response to determining that the requesting the scheduling of theresources comprises requesting the scheduling data for a multicasttransmission, multicasting a transmission to the receiver user equipmentdevice.
 13. The transmitter user equipment device of claim 11, whereinthe communicating comprises, in response to determining that therequesting the scheduling of the resources comprises requesting thescheduling data for a unicast transmission to the receiver userequipment device, identifying the receiver user equipment device to thescheduler user equipment device, and unicasting a transmission to thereceiver user equipment device.
 14. The transmitter user equipmentdevice of claim 11, wherein the communicating comprises, in response todetermining that the requesting the scheduling of the resourcescomprises requesting the scheduling data for transmission of cellulardata to the scheduler user equipment device, operating the transmitteruser equipment device as an access link with respect to the receiveruser equipment device.
 15. A non-transitory machine-readable medium,comprising executable instructions that, when executed by a processor ofa local manager radio user equipment, facilitate performance ofoperations, the operations comprising: receiving, from a network devicecoupled to the local manager radio user equipment, radio user equipmentcommunication resource scheduling data; receiving, from a transmitteruser equipment that is in a group managed by the local manager radiouser equipment, a request to schedule the transmitter user equipmentwith scheduling information, wherein the request is associated withtraffic type information; and scheduling the transmitter user equipmentbased on the radio user equipment communication resource scheduling dataand the traffic type information, to facilitate a transmission of datafrom the transmitter user equipment to a receiver user equipment,wherein the scheduling comprises, in response to determining that thetraffic type information corresponds to unicast information, receivingan identifier of the receiver user equipment, and scheduling thereceiver user equipment based on the radio user equipment communicationresource scheduling data and the traffic type information, to facilitatethe transmission to be a direct transmission of the data from thetransmitter user equipment to the receiver user equipment.
 16. Thenon-transitory machine-readable medium of claim 15, wherein in responseto determining that the traffic type information corresponds to cellulardata information, receiving the transmission comprising cellular datafrom the transmitter user equipment at the local manager radio userequipment, and relaying the cellular data to the network device.
 17. Thenon-transitory machine-readable medium of claim 15, wherein in responseto determining that the receiver user equipment is in a different groupmanaged by a different local manager radio user equipment, coordinatingwith the different local manager radio user equipment to facilitate thetransmission of the data from the transmitter user equipment to thereceiver user equipment.
 18. The non-transitory machine-readable mediumof claim 15, wherein the scheduling the transmitter user equipmentcomprises transmitting scheduling information to the transmitter userequipment.
 19. The non-transitory machine-readable medium of claim 18,wherein the transmitting the scheduling information to the transmitteruser equipment comprises transmitting the scheduling information asdownlink control information to the transmitter user equipment.
 20. Thetransmitter user equipment device of claim 11, wherein the receiving thescheduling data comprises receiving the scheduling data as downlinkcontrol information.